Gradual image display

ABSTRACT

Systems and techniques for displaying an image sent between subscribers of a communications system by receiving electronic data corresponding to the image; displaying a blurred view of the image; and gradually displaying a sharper version of the image in response to user input.

This application claims the benefit of U.S. Provisional Application No.60/215,765 filed Jun. 30, 2000.

TECHNICAL FIELD

The present invention relates generally to transferring files betweensubscribers of a communications system.

BACKGROUND

Online service providers are constantly offering new services andupgrading existing services to enhance their subscribers' onlineexperience. Subscribers have virtually on-demand access to news,weather, financial, sports, and entertainment services as well as theability to transmit electronic messages and to participate in onlinediscussion groups. For example, subscribers of online service providerssuch as America Online or CompuServe may view and retrieve informationon a wide variety of topics from servers located throughout the world. Aserver may be maintained by the service provider or by a third partyprovider who makes information and services available through theworldwide network of computers that make up the online service.

America Online has provided subscribers with the ability to send andreceive instant messages. Instant messages are private onlineconversations between two or more people who have subscribed to theinstant messaging service and have installed the necessary software.Because such online conversations take place virtually in real time,instant messaging can provide immediate access to desired information.Instant messaging is becoming a preferred means of communicating amongonline subscribers.

SUMMARY

In one general aspect, an image sent between subscribers of acommunications system is displayed by receiving electronic datacorresponding to the image; displaying a blurred view of the image; andgradually displaying a sharper version of the image in response to userinput.

Implementations may include displaying a blurred view of the image bypartially rendering the image data; setting preferences for receivingimages; and allowing the user to reject the image. A graphic userinterface may be presented to the user for setting preferences and/orrejecting the images.

The communications system may be an instant messaging system. The imagedata may be received as an instant message and/or compressed tostandardized image size. An instant message may be displayedconcurrently with the blurred view and/or the sharpened view of theimage in a separate dialog box. The image may be an icon and may beassociated with a sender of an instant message and/or an e-mail message.

Embodiments may be implemented by an apparatus and/or by a computerprogram stored on a computer readable medium. The computer readablemedium may be a disc, a client device, a host device, and/or apropagated signal.

Other features and advantages will be apparent from the followingdescription, including the drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a communications system.

FIGS. 2-6 are expansions of aspects the block diagram of FIG. 1.

FIG. 7 is a flow chart of a communications method.

FIGS. 8-11 are illustrations of different graphical user interfaces.

DETAILED DESCRIPTION

For illustrative purposes, FIGS. 1-6 describe a communications systemfor implementing techniques for displaying an image sent betweensubscribers of a communications system. For brevity, several elements inthe figures described below are represented as monolithic entities.However, as would be understood by one skilled in the art, theseelements each may include numerous interconnected computers andcomponents designed to perform a set of specified operations and/ordedicated to a particular geographical region.

Referring to FIG. 1, a communications system 100 is capable ofdelivering and exchanging data between a client system 105 and a hostsystem 110 through a communications link 115. The client system 105typically includes one or more client devices 120 and/or clientcontrollers 125. For example, the client system 105 may include one ormore general-purpose computers (e.g., personal computers), one or morespecial-purpose computers (e.g., devices specifically programmed tocommunicate with each other and/or the host system 110), or acombination of one or more general-purpose computers and one or morespecial-purpose computers. The client system 105 may be arranged tooperate within or in concert with one or more other systems, such as forexample, one or more LANs (“Local Area Networks”) and/or one or moreWANs (“Wide Area Networks”).

The client device 120 is generally capable of executing instructionsunder the command of a client controller 125. The client device 120 isconnected to the client controller 125 by a wired or wireless datapathway 130 capable of delivering data.

The client device 120 and client controller 125 each typically includesone or more hardware components and/or software components. An exampleof a client device 120 is a general-purpose computer (e.g., a personalcomputer) capable of responding to and executing instructions in adefined manner. Other examples include a special-purpose computer, aworkstation, a server, a device, a component, other equipment or somecombination thereof capable of responding to and executing instructions.An example of client controller 125 is a software application loaded onthe client device 120 for commanding and directing communicationsenabled by the client device 120. Other examples include a program, apiece of code, an instruction, a device, a computer, a computer system,or a combination thereof, for independently or collectively instructingthe client device 120 to interact and operate as described herein. Theclient controller 125 may be embodied permanently or temporarily in anytype of machine, component, equipment, storage medium, or propagatedsignal capable of providing instructions to the client device 120.

The communications link 115 typically includes a delivery network 160making a direct or indirect communication between the client system 105and the host system 110, irrespective of physical separation. Examplesof a delivery network 160 include the Internet, the World Wide Web,WANs, LANs, analog or digital wired and wireless telephone networks(e.g. PSTN, ISDN, or xDSL), radio, television, cable, satellite, and/orany other delivery mechanism for carrying data. The communications link115 may include communication pathways 150, 155 that enablecommunications through the one or more delivery networks 160 describedabove. Each of the communication pathways 150, 155 may include, forexample, a wired, wireless, cable or satellite communication pathway.

The host system 110 includes a host device 135 capable of executinginstructions under the command and direction of a host controller 140.The host device 135 is connected to the host controller 140 by a wiredor wireless data pathway 145 capable of carrying and delivering data.

The host system 110 typically includes one or more host devices 135and/or host controllers 140. For example, the host system 110 mayinclude one or more general-purpose computers (e.g., personalcomputers), one or more special-purpose computers (e.g., devicesspecifically programmed to communicate with each other and/or the clientsystem 105), or a combination of one or more general-purpose computersand one or more special-purpose computers. The host system 110 may bearranged to operate within or in concert with one or more other systems,such as, for example, one or more LANs (“Local Area Networks”) and/orone or more WANs (“Wide Area Networks”).

The host device 135 and host controller 140 each typically includes oneor more hardware components and/or software components. An example of ahost device 135 is a general-purpose computer (e.g., a personalcomputer) capable of responding to and executing instructions in adefined manner. Other examples include a special-purpose computer, aworkstation, a server, a device, a component, other equipment or somecombination thereof capable of responding to and executing instructions.An example of host controller 140 is a software application loaded onthe host device 135 for commanding and directing communications enabledby the host device 135. Other examples include a program, a piece ofcode, an instruction, a device, a computer, a computer system, or acombination thereof, for independently or collectively instructing thehost device 135 to interact and operate as described herein. The hostcontroller 140 may be embodied permanently or temporarily in any type ofmachine, component, equipment, storage medium, or propagated signalcapable of providing instructions to the host device 135.

FIG. 2 illustrates a communication system 200 including a client system205 communicating with a host system 210 through a communications link215. Client system 205 typically includes one or more client devices 220and one or more client controllers 225 for controlling the clientdevices 220. Host system 210 typically includes one or more host devices235 and one or more host controllers 240 for controlling the hostdevices 235. The communications link 215 may include communicationpathways 250, 255 enabling communications through the one or moredelivery networks 260.

Examples of each element within the communication system of FIG. 2 arebroadly described above with respect to FIG. 1. In particular, the hostsystem 210 and communications link 215 typically have attributescomparable to those described with respect to host system 110 andcommunications link 115 of FIG. 1. Likewise, the client system 205 ofFIG. 2 typically has attributes comparable to and illustrates onepossible embodiment of the client system 105 of FIG. 1.

The client device 220 typically includes a general purpose computer 270having an internal or external storage 272 for storing data and programssuch as an operating system 274 (e.g., DOS, Windows™, Windows 95™,Windows 98™, Windows 2000™, Windows NT™, OS/2, or Linux) and one or moreapplication programs. Examples of application programs include authoringapplications 276 (e.g., word processing, database programs, spreadsheetprograms, or graphics programs) capable of generating documents or otherelectronic content; client applications 278 (e.g., AOL client,CompuServe client, AIM client, AOL TV client, or ISP client) capable ofcommunicating with other computer users, accessing various computerresources, and viewing, creating, or otherwise manipulating electroniccontent; and browser applications 280 (e.g., Netscape's Navigator orMicrosoft's Internet Explorer) capable of rendering standard Internetcontent.

The general-purpose computer 270 also includes a central processing unit282 (CPU) for executing instructions in response to commands from theclient controller 225. In one implementation, the client controller 225includes one or more of the application programs installed on theinternal or external storage 272 of the general-purpose computer 270. Inanother implementation, the client controller 225 includes applicationprograms externally stored in and performed by one or more device(s)external to the general-purpose computer 270.

The general-purpose computer typically will include a communicationdevice 284 for sending and receiving data. One example of thecommunication device 284 is a modem. Other examples include atransceiver, a set-top box, a communication card, a satellite dish, anantenna, or another network adapter capable of transmitting andreceiving data over the communications link 215 through a wired orwireless data pathway 250. The general-purpose computer 270 also mayinclude a TV (“television”) tuner 286 for receiving televisionprogramming in the form of broadcast, satellite, and/or cable TVsignals. As a result, the client device 220 can selectively and/orsimultaneously display network content received by communications device284 and television programming content received by the TV tuner 286.

The general-purpose computer 270 typically will include an input/outputinterface 288 for wired or wireless connection to various peripheraldevices 290. Examples of peripheral devices-290 include, but are notlimited to, a mouse 291, a mobile phone 292, a personal digitalassistant 293 (PDA), a keyboard 294, a display monitor 295 with orwithout a touch screen input, and/or a TV remote control 296 forreceiving information from and rendering information to subscribers.

Although FIG. 2 illustrates devices such as a mobile telephone 292, aPDA 293, and a TV remote control 296 as being peripheral with respect tothe general-purpose computer 270, in another implementation, suchdevices may themselves include the functionality of the general-purposecomputer 270 and operate as the client device 220. For example, themobile phone 292 or the PDA 293 may include computing and networkingcapabilities and function as a client device 220 by accessing thedelivery network 260 and communicating with the host system 210.Furthermore, the client system 205 may include one, some or all of thecomponents and devices described above.

Referring to FIG. 3, a communications system 300 is capable ofdelivering and exchanging information between a client system 305 and ahost system 310 through a communication link 315. Client system 305typically includes one or more client devices 320 and one or more clientcontrollers 325 for controlling the client devices 320. Host system 310typically includes one or more host devices 335 and one or more hostcontrollers 340 for controlling the host devices 335. The communicationslink 315 may include communication pathways 350, 355 enablingcommunications through the one or more delivery networks 360.

Examples of each element within the communication system of FIG. 3 arebroadly described above with respect to FIGS. 1 and 2. In particular,the client system 305 and the communications link 315 typically haveattributes comparable to those described with respect to client systems105 and 205 and communications links 115 and 215 of FIGS. 1 and 2.Likewise, the host system 310 of FIG. 3 may have attributes comparableto and illustrates one possible embodiment of the host systems 110 and210 shown in FIGS. 1 and 2, respectively.

The host system 310 includes a host device 335 and a host controller340. The host controller 340 is generally capable of transmittinginstructions to any or all of the elements of the host device 335. Forexample, in one implementation, the host controller 340 includes one ormore software applications loaded on the host device 335. However, inother implementations, as described above, the host controller 340 mayinclude any of several other programs, machines, and devices operatingindependently or collectively to control the host device 335.

The host device 335 includes a login server 370 for enabling access bysubscribers and routing communications between the client system 305 andother elements of the host device 335. The host device 335 also includesvarious host complexes such as the depicted OSP (“Online ServiceProvider”) host complex 380 and IM (“Instant Messaging”) host complex390. To enable access to these host complexes by subscribers, the clientsystem 305 includes communication software, for example, an OSP clientapplication and an IM client application. The OSP and IM communicationsoftware applications are designed to facilitate the subscriber'sinteractions with the respective services and, in particular, mayprovide access to all the services available within the respective hostcomplexes.

Typically, the OSP host complex 380 supports different services, such asemail, discussion groups, chat, news services, and Internet access. TheOSP host complex 380 is generally designed with an architecture thatenables the machines within the OSP host complex 380 to communicate witheach other and employs certain protocols (i.e., standards, formats,conventions, rules, and structures) to transfer data. The OSP hostcomplex 380 ordinarily employs one or more OSP protocols and customdialing engines to enable access by selected client applications. TheOSP host complex 380 may define one or more specific protocols for eachservice based on a common, underlying proprietary protocol.

The IM host complex 390 is generally independent of the OSP host complex380, and supports instant messaging services irrespective of asubscriber's network or Internet access. Thus, the IM host complex 390allows subscribers to send and receive instant messages, whether or notthey have access to any particular ISP. The IM host complex 390 maysupport associated services, such as administrative matters,advertising, directory services, chat, and interest groups related tothe instant messaging. The IM host complex 390 has an architecture thatenables all of the machines within the IM host complex to communicatewith each other. To transfer data, the IM host complex 390 employs oneor more standard or exclusive IM protocols.

The host device 335 may include one or more gateways that connect andtherefore link complexes, such as the OSP host complex gateway 385 andthe IM host complex gateway 395. The OSP host complex gateway 385 andthe IM host complex 395 gateway may directly or indirectly link the OSPhost complex 380 with the IM host complex 390 through a wired orwireless pathway. Ordinarily, when used to facilitate a link betweencomplexes, the OSP host complex gateway 385 and the IM host complexgateway 395 are privy to information regarding the protocol typeanticipated by a destination complex, which enables any necessaryprotocol conversion to be performed incident to the transfer of datafrom one complex to another. For instance, the OSP host complex 380 andIM host complex 390 generally use different protocols such thattransferring data between the complexes requires protocol conversion byor at the request of the OSP host complex gateway 385 and/or the IM hostcomplex gateway 395.

Referring to FIG. 4, a communications system 400 is capable ofdelivering and exchanging information between a client system 405 and ahost system 410 through a communication link 415. Client system 405typically includes one or more client devices 420 and one or more clientcontrollers 425 for controlling the client devices 420. Host system 410typically includes one or more host devices 435 and one or more hostcontrollers 440 for controlling the host devices 435. The communicationslink 415 may include communication pathways 450, 455 enablingcommunications through the one or more delivery networks 460. As shown,the client system 405 may access the Internet 465 through the hostsystem 410.

Examples of each element within the communication system of FIG. 4 arebroadly described above with respect to FIGS. 1-3. In particular, theclient system 405 and the communications link 415 typically haveattributes comparable to those described with respect to client systems105, 205, and 305 and communications links 115, 215, and 315 of FIGS.1-3. Likewise, the host system 410 of FIG. 4 may have attributescomparable to and illustrates one possible embodiment of the hostsystems 110, 210, and 310 shown in FIGS. 1-3, respectively. However,FIG. 4 describes an aspect of the host system 410, focusing primarily onone particular implementation of OSP host complex 480. For purposes ofcommunicating with an OSP host complex 480, the delivery network 460 isgenerally a telephone network.

The client system 405 includes a client device 420 and a clientcontroller 425. The client controller 425 is generally capable ofestablishing a connection to the host system 410, including the OSP hostcomplex 480, the IM host complex 490 and/or the Internet 465. In oneimplementation, the client controller 425 includes an OSP applicationfor communicating with servers in the OSP host complex 480 usingexclusive OSP protocols. The client controller 425 also may includeapplications, such as an IM client application, and/or an Internetbrowser application, for communicating with the IM host complex 490 andthe Internet 465.

The host system 410 includes a host device 435 and a host controller440. The host controller 440 is generally capable of transmittinginstructions to any or all of the elements of the host device 435. Forexample, in one implementation, the host controller 440 includes one ormore software applications loaded on one or more elements of the hostdevice 435. However, in other implementations, as described above, thehost controller 440 may include any of several other programs, machines,and devices operating independently or collectively to control the hostdevice 435.

The host system 410 includes a login server 470 capable of enablingcommunications with and authorizing access by client systems 405 tovarious elements of the host system 410, including an OSP host complex480 and an IM host complex 490. The login server 470 may implement oneor more authorization procedures to enable simultaneous access to theOSP host complex 480 and the IM host complex 490. The OSP host complex480 and the IM host complex 490 are connected through one or more OSPhost complex gateways 485 and one or more IM host complex gateways 495.Each OSP host complex gateway 485 and IM host complex gateway 495 mayperform any protocol conversions necessary to enable communicationbetween the OSP host complex 480, the IM host complex 490, and theInternet 465.

The OSP host complex 480 supports a set of services from one or moreservers located internal to and external from the OSP host complex 480.Servers external to the OSP host complex 480 generally communicatethrough the Internet 465. Servers internal to the OSP complex 480 may bearranged in one or more configurations. For example, servers may bearranged in large centralized clusters known as farms 4802 or inlocalized clusters known as pods 4804.

Farms 4802 are groups of servers located at centralized locations withinthe OSP host complex 480. Farms 4802 generally are dedicated toproviding particular functionality and services to subscribers andclients from a centralized location, regardless of the location of thesubscriber or client. Farms 4802 are particularly useful for providingservices that depend upon other processes and services for information,such as, for example, chat, email, instant messaging, news, newsgroups,search, stock updates, and weather. Thus, farms 4802 tend to rely onconnections with external resources such as the Internet 465 and/orother servers within the OSP host complex 480.

To reduce the time delays and congestion inherent in centralizedprocessing, some services offered by the OSP host complex 480 areprovided from localized servers, generally known as pods 4804. Each pod4804 includes one or more interrelated servers capable of operatingtogether to provide one or more services offered by the OSP host complex480 in a geographically localized manner, the servers within a pod 4804generally operating independently rather than relying on resourcesexternal to the pod 4804 to operate. A pod 4804 may cache contentreceived from external sources, such as farms 4802 or the Internet 465,making frequently requested information readily available to localsubscribers served by the pod 4804. In this way, pods 4804 areparticularly useful in providing services that are independent of otherprocesses and servers such as, for example, routing, keywords, anddownloading certain software and graphical interface updates withreduced processing time and congestion. The determination of whichservers and processes are located in the pod 4804 is made by the OSPaccording to load distribution, frequency of requests, demographics, andother factors.

In addition to farms 4802 and pods 4804, the implementation of FIG. 4also includes one or more non-podded servers 4806. In general, thenon-podded server 4806 may be dedicated to performing a particularservice that relies on other processes and services for information andmay be directly or indirectly connected to resources outside of the OSPhost complex 480, such as the Internet 465 and the IM host complex 490,through an OSP gateway 4808. In the event that subscriber usage of theparticular service is relatively high, the non-podded server 4806 may beincluded in a farm.

In the implementation of FIG. 4, a pod 4810, shown in more detail,includes a routing processor 4812. In a packet-based implementation, theclient system 405 may generate information requests, convert therequests into data packets, sequence the data packets, perform errorchecking and other packet-switching techniques, and transmit the datapackets to the routing processor 4812. Upon receiving data packets fromthe client system 405, the routing processor 4812 may directly orindirectly route the data packets to a specified destination within oroutside of the OSP host complex 480. In general, the routing processor4812 will examine an address field of a data request, use a mappingtable to determine the appropriate destination for the data request, anddirect the data request to the appropriate destination.

For example, in the event that a data request from the client system 405can be satisfied locally, the routing processor 4812 may direct the datarequest to a local server 4814 in the pod 4810. In the event that thedata request cannot be satisfied locally, the routing processor 4812 maydirect the data request internally to one or more farms 4802, one ormore other pods 4804, or one or more non-podded servers 4806 in the OSPhost complex 480 or may direct the data request externally to theInternet 465 or the IM host complex 490 through an OSP/pod gateway 4816.

The routing processor 4812 also may direct data requests and/orotherwise facilitate communication between the client system 405 and theInternet 465. In one implementation, the client system 405 uses an OSPclient application to convert standard Internet content and protocolsinto OSP protocols and vice versa. For example, when a browserapplication transmits a request in standard Internet protocol, the OSPclient application can intercept the request, convert the request intoan OSP protocol and send the converted request to the routing processor4812 in the OSP host complex 480. The routing processor 4812 recognizesthe Internet 465 as the destination and routes the data packets to an IP(“Internet Protocol”) tunnel 4818. The IP tunnel 4818 converts the datafrom the OSP protocol back into standard Internet protocol and transmitsthe data to the Internet 465. The IP tunnel 4818 also converts the datareceived from the Internet in the standard Internet protocol back intothe OSP protocol and sends the data to the routing processor 4812 fordelivery back to the client system 405. At the client system 405, theOSP client application converts the data in the OSP protocol back intostandard Internet content for communication with the browserapplication.

The IP tunnel 4818 may act as a buffer between the client system 405 andthe Internet 465, and may implement content filtering and time savingtechniques. For example, the IP tunnel 4818 can check parental controlssettings of the client system 405 and request and transmit content fromthe Internet 465 according to the parental control settings. Inaddition, the IP tunnel 4818 may include a number a caches for storingfrequently accessed information. If requested data is determined to bestored in the caches, the IP tunnel 4818 may send the information to theclient system 405 from the caches and avoid the need to access theInternet 465.

In another implementation, the client system 405 may use standardInternet protocols and formatting to access the pod 4810 and theInternet 465. For example, the subscriber can use an OSP TV clientapplication having an embedded browser application installed on theclient system 405 to generate a request in standard Internet protocol,such as HTTP (“HyperText Transport Protocol”). In a packet-basedimplementation, data packets may be encapsulated inside a standardInternet tunneling protocol, such as, for example, UDP (“User DatagramProtocol”) and routed to a web tunnel 4820. The web tunnel 4820 may be aL2TP (“Layer Two Tunneling Protocol”) tunnel capable of establishing apoint-to-point protocol (PPP) session with the client system 405. Theweb tunnel 4820 provides a gateway to the routing processor 4812 withinthe pod 4810, the Internet 465, and a web proxy 4822.

The web proxy 4822 can look up subscriber information from the IPaddress of the client system 405 to determine the subscriber's parentalcontrols settings and other demographic information. In this way, theweb proxy 4822 can tailor the subscriber's content and user interfaces.The web proxy 4822 can also perform caching functions to store certainURLs (“Uniform Resource Locators”) and other electronic content so thatthe web proxy 4822 can locally deliver information to the client system405 and avoid the need to access the Internet 465 in the event that datarequested by the client system 405 has been cached.

Referring to FIG. 5, a communications system 500 is capable ofdelivering and exchanging information between a client system 505 and ahost system 510 through a communication link 515. Client system 505typically includes one or more client devices 520 and one or more clientcontrollers 525 for controlling the client devices 520. Host system 510typically includes one or more host devices 535 and one or more hostcontrollers 540 for controlling the host devices 535. The communicationslink 515 may include communication pathways 550, 555 enablingcommunications through the one or more delivery networks 560. As shown,the client system 505 may access the Internet 565 through the hostsystem 510.

Examples of each element within the communication system of FIG. 5 arebroadly described above with respect to FIGS. 1-4. In particular, theclient system 505 and the communications link 515 typically haveattributes comparable to those described with respect to client systems105, 205, 305, and 405 and communications links 115, 215, 315, and 415of FIGS. 1-4. Likewise, the host system 510 of FIG. 5 may haveattributes comparable to and illustrates one possible embodiment of thehost systems 110, 210, 310, and 410 shown in FIGS. 1-4, respectively.However, FIG. 5 describes an aspect of the host system 510, focusingprimarily on one particular implementation of IM host complex 590. Forpurposes of communicating with the IM host complex 590, the deliverynetwork 560 is generally a telephone network.

The client system 505 includes a client device 520 and a clientcontroller 525. The client controller 525 is generally capable ofestablishing a connection to the host system 510, including the OSP hostcomplex 580, the IM host complex 590 and/or the Internet 565. In oneimplementation, the client controller 525 includes an IM application forcommunicating with servers in the IM host complex 590 utilizingexclusive IM protocols. The client controller 525 also may includeapplications, such as an OSP client application, and/or an Internetbrowser application for communicating with the OSP host complex 580 andthe Internet 565, respectively.

The host system 510 includes a host device 535 and a host controller540. The host controller 540 is generally capable of transmittinginstructions to any or all of the elements of the host device 535. Forexample, in one implementation, the host controller 540 includes one ormore software applications loaded on one or more elements of the hostdevice 535. However, in other implementations, as described above, thehost controller 540 may include any of several other programs, machines,and devices operating independently or collectively to control the hostdevice 535.

The host system 510 includes a login server 570 capable of enablingcommunications with and authorizing access by client systems 505 tovarious elements of the host system 510, including an OSP host complex580 and an IM host complex 590. The login server 570 may implement oneor more authorization procedures to enable simultaneous access to theOSP host complex 580 and the IM host complex 590. The OSP host complex580 and the IM host complex 590 are connected through one or more OSPhost complex gateways 585 and one or more IM host complex gateways 595.Each OSP host complex gateway 585 and IM host complex gateway 595 mayperform any protocol conversions necessary to enable communicationbetween the OSP host complex 580, the IM host complex 590, and theInternet 565.

To access the IM host complex 590 to begin an instant messaging session,the client system 505 establishes a connection to the login server 570.The login server 570 typically determines whether the particularsubscriber is authorized to access the IM host complex 590 by verifyinga subscriber identification and password. If the subscriber isauthorized to access the IM host complex 590, the login server 570employs a hashing technique on the subscriber's screen name to identifya particular IM server 5902 for use during the subscriber's session. Thelogin server 570 provides the client system 505 with the IP address ofthe particular IM server 5902, gives the client system 505 an encryptedkey (i.e., a cookie), and breaks the connection. The client system 505then uses the IP address to establish a connection to the particular IMserver 5902 through the communications link 515, and obtains access tothat IM server 5902 using the encrypted key. Typically, the clientsystem 505 will be equipped with a Winsock API (“Application ProgrammingInterface”) that enables the client system 505 to establish an open TCPconnection to the IM server 5902.

Once a connection to the IM server 5902 has been established, the clientsystem 505 may directly or indirectly transmit data to and accesscontent from the IM server 5902 and one or more associated domainservers 5904. The IM server 5902 supports the fundamental instantmessaging services and the domain servers 5904 may support associatedservices, such as, for example, administrative matters, directoryservices, chat and interest groups. In general, the purpose of thedomain servers 5904 is to lighten the load placed on the IM server 5902by assuming responsibility for some of the services within the IM hostcomplex 590. By accessing the IM server 5902 and/or the domain server5904, a subscriber can use the IM client application to view whetherparticular subscribers (“buddies”) are online, exchange instant messageswith particular subscribers, participate in group chat rooms, tradefiles such as pictures, invitations or documents, find other subscriberswith similar interests, get customized news and stock quotes, and searchthe Web.

In the implementation of FIG. 5, the IM server 5902 is directly orindirectly connected to a routing gateway 5906. The routing gateway 5906facilitates the connection between the IM server 5902 and one or morealert multiplexors 5908, for example, by serving as a link minimizationtool or hub to connect several IM servers to several alert multiplexors.In general, an alert multiplexor 5908 maintains a record of alerts andsubscribers registered to receive the alerts.

Once the client system 505 is connected to the alert multiplexor 5908, asubscriber can register for and/or receive one or more types of alerts.The connection pathway between the client system 505 and the alertmultiplexor 5908 is determined by employing another hashing technique atthe IM server 5902 to identify the particular alert multiplexor 5908 tobe used for the subscriber's session. Once the particular multiplexor5908 has been identified, the IM server 5902 provides the client system505 with the IP address of the particular alert multiplexor 5908 andgives the client system 505 an encrypted key (i.e., a cookie). Theclient system 505 then uses the IP address to connect to the particularalert multiplexor 5908 through the communication link 515 and obtainsaccess to the alert multiplexor 5908 using the encrypted key.

The alert multiplexor 5908 is connected to an alert gate 5910 that, likethe IM host complex gateway 595, is capable of performing the necessaryprotocol conversions to form a bridge to the OSP host complex 580. Thealert gate 5910 is the interface between the IM host complex 590 and thephysical servers, such as servers in the OSP host complex 580, wherestate changes are occurring. In general, the information regarding statechanges will be gathered and used by the IM host complex 590. However,the alert multiplexor 5908 also may communicate with the OSP hostcomplex 580 through the IM gateway 595, for example, to provide theservers and subscribers of the OSP host complex 580 with certaininformation gathered from the alert gate 5910.

The alert gate 5910 can detect an alert feed corresponding to aparticular type of alert. The alert gate 5910 may include a piece ofcode (alert receive code) capable of interacting with another piece ofcode (alert broadcast code) on the physical server where a state changeoccurs. In general, the alert receive code installed on the alert gate5910 instructs the alert broadcast code installed on the physical serverto send an alert feed to the alert gate 5910 upon the occurrence of aparticular state change. Upon detecting an alert feed, the alert gate5910 contacts the alert multiplexor 5908, which in turn, informs theclient system 505 of the detected alert feed.

In the implementation of FIG. 5, the IM host complex 590 also includes asubscriber profile server 5912 connected to a database 5914 for storinglarge amounts of subscriber profile data. The subscriber profile server5912 may be used to enter, retrieve, edit, manipulate, or otherwiseprocess subscriber profile data. In one implementation, a subscriber'sprofile data includes, for example, the subscriber's buddy list, alertpreferences, designated stocks, identified interests, and geographiclocation. The subscriber may enter, edit and/or delete profile datausing an installed IM client application on the client system 505 tointeract with the subscriber profile server 5912.

Because the subscriber's data is stored in the IM host complex 590, thesubscriber does not have to reenter or update such information in theevent that the subscriber accesses the IM host complex 590 using new ora different client system 505. Accordingly, when a subscriber accessesthe IM host complex 590, the IM server 5902 can instruct the subscriberprofile server 5912 to retrieve the subscriber's profile data from thedatabase 5914 and to provide, for example, the subscriber's buddy listto the IM server 5902 and the subscriber's alert preferences to thealert multiplexor 5908. The subscriber profile server 5912 also maycommunicate with other servers in the OSP host complex 590 to sharesubscriber profile data with other services. Alternatively, user profiledata may be saved locally on the client device 505.

Referring to FIG. 6, a communications system 600 is capable ofdelivering and exchanging information between a client system 605 and ahost system 610 through a communication link 615. Client system 605typically includes one or more client devices 620 and one or more clientcontrollers 625 for controlling the client devices 620. Host system 610typically includes one or more host devices 635 and one or more hostcontrollers 640 for controlling the host devices 635. The communicationslink 615 may include communication pathways 650, 655 enablingcommunications through the one or more delivery networks 660.

Examples of each element within the communication system of FIG. 6 arebroadly described above with respect to FIGS. 1-5. In particular, theclient system 605 and the communications link 615 typically haveattributes comparable to those described with respect to client systems105, 205, 305, 405 and 505 and communications links 115, 215, 315, 415and 515 of FIGS. 1-5. Likewise, the host system 610 of FIG. 6 may haveattributes comparable to and illustrates one possible embodiment of thehost systems 110, 210, 310, 410 and 510 shown in FIGS. 1-5,respectively. However, FIG. 6 describes an aspect of the host system610, focusing primarily on one particular implementation of IM hostcomplex 690.

The client system 605 includes a client device 620 and a clientcontroller 625. The client controller 625 is generally capable ofestablishing a connection to the host system 610, including the IM hostcomplex 690. In one implementation, the client controller 625 includesan IM application for communicating with servers in the IM host complex690 utilizing exclusive IM protocols.

The host system 610 includes a host device 635 and a host controller640. The host controller 640 is generally capable of transmittinginstructions to any or all of the elements of the host device 635. Forexample, in one implementation, the host controller 640 includes one ormore software applications loaded on one or more elements of the hostdevice 635. However, in other implementations, as described above, thehost controller 640 may include any of several other programs, machines,and devices operating independently or collectively to control the hostdevice 635.

The host system 610 includes a login server 670 capable of enablingcommunications with and authorizing access by client systems 605 tovarious elements of the host system 610, including the IM host complex690. The IM host complex 690 includes an IM server network 6902 and analert multiplexor network 6908. The IM server network 6902 is aninterconnected network of IM servers and the alert multiplexor network6908 is an interconnected network of alert multiplexors. Each IM serverand each alert multiplexor can directly or indirectly communicate andexchange information with all of the IM servers in the IM server network6902 and all of the alert multiplexors in the alert multiplexor network6908. Each of the alert multiplexors in the alert multiplexor network6908 is connected to several alert gates 6910 that receive differenttypes of alerts. In the implementation of FIG. 6, the IM server network6902 and the alert multiplexor network 6908 are interconnected by arouting gateway 6906 that serves as a common hub to reduce the number ofconnections.

A subscriber typically will be assigned to one IM server in the IMserver network 6902 and to one alert multiplexor in the alertmultiplexor network 6908 during a session based on one or more hashingtechniques. However, the IM servers and the alert multiplexors arecapable of storing subscriber information and other electronic contentthat may be accessed by the other IM servers and alert multiplexors. Inone implementation, for example, each IM server in the IM server network6902 may be dedicated to serving a particular set of registeredsubscribers. Because all of the IM servers can communicate with eachother, all subscribers can communicate with each other through instantmessaging. In another implementation, each alert multiplexor in thealert multiplexor network 6908 may be dedicated to storing informationabout a particular set or subset of alerts. Because all of the alertmultiplexors can communicate with each other, all registered subscriberscan receive all types of alerts. This networking arrangement enables theload to be distributed among the various servers in the IM host complex690 while still enabling a subscriber to communicate, share information,or otherwise interact with other subscribers and servers in the IM hostcomplex 690.

Referring to FIG. 7, a first client 702 a, a second client 702 b, and ahost 704 interact according to a procedure 700 to enable and graduallydisplay “buddy icons.” Buddy icons are images such as cartooncharacters, symbols, pictures, and other graphical images thatsubscribers can use to represent themselves or other buddies in theirBuddy List®. In one implementation, buddy icons appear in the lower-leftcorner of instant messaging windows when subscribers send messages backand forth to each other.

The procedure 700 may be implemented by any suitable type of hardware,software, device, computer, computer system, equipment, component,program, application, code, storage medium, or propagated signal.

Examples of each element of FIG. 7 are broadly described above withrespect to FIGS. 1-6. In particular, the first client 702 a and thesecond client 702 b typically have attributes comparable to thosedescribed with respect to client devices 120, 220, 320, 420, 520 and 620and/or client controllers 125, 225, 325, 425, 525 and 625. The host 704typically has attributes comparable to those described with respect tohost device 135, 235, 335, 435, 535 and 635 and/or host controllers 140,240, 340, 440, 540 and 640. The first client 702 a, the second client702 b, and/or the host 704 may be directly or indirectly interconnectedthrough a known or described delivery network.

Each of the clients 702 a, 702 b is associated with a subscriber. Toenable buddy icons, each subscriber selects a buddy icon and then setscertain transfer preferences for permitting buddy icons to betransferred to and from other subscribers. For example, a firstsubscriber may set transfer preferences governing which screen names orsubscribers can send buddy icons to client 702 a. Likewise, a secondsubscriber may set transfer preferences governing which screen names orsubscribers can send buddy icons to client 702 b. Typically, eachsubscriber will be presented with a graphical UI (“User Interface”) thatpermits the subscriber to select a buddy icon and set various transferpreferences. A subscriber's transfer preferences may be maintainedlocally or on the host 704.

Initially, the first subscriber selects a graphical image (step 710).The graphical image may be selected from any of the images displayed bya browser when connecting to an OSP or the Internet. The firstsubscriber then installs the graphics file associated with the graphicalimage on the client 702 a (step 715). In one implementation, the firstsubscriber saves the graphics file in a directory specificallydesignated for buddy icons on the client 702 a. The first subscriberdesignates the selected graphical image as a buddy icon for the firstsubscriber (step 720 a). Typically, the first subscriber will bepresented with a UI to perform this designation.

The IM client application will size the graphical image to conform tostandard buddy icon size. In one implementation, graphical images arestandardized to 48×48 pixels. Formats for the graphics files include,but are not limited to .BMP (bit-mapped), GIF (graphics interchangeformat), .JPEG (joint photographic experts group), .ICO (icon), and .XBM(X bit map) file formats. In general, there is no limit to the heightand width of the graphical image designated as a buddy icon.

There may, however, be a disk space limitation for graphical imagesdesignated as buddy icons. In one implementation, the image cannot usemore than 7168 bytes of disk space due to the limited capacity of theconnection between the clients 702 a, 702 b and the host 704. Thelimited capacity of the connection is designed to prevent objectionableimages from being sent to subscribers through the IM host since mostimages require more than 8 kilobytes of disk space. The rationale isthat the real-time quality of instant messaging affords littleopportunity to monitor or screen images sent between subscribers.Therefore, it is safer for subscribers if the host 704 prevents imagesfrom being sent through the IM host. As described above, images may betransferred between subscribers only when the clients are directlyconnected through a socket connection, for example. Typically,subscribers will allow only trusted persons to directly connect to theircomputers.

Even though the host 704 prevents images from being sent in an instantmessage dialogue box, there is still the danger that a subscriber willchoose a buddy icon that other subscribers find objectionable. To reducethe danger of a subscriber viewing an objectionable image, the client702 b gradually displays the buddy icon sent from another subscriber andaffords the opportunity to accept or reject the buddy icon. This processwill be described in more detail below.

At the second client 702 b, the second subscriber selects buddy iconpreferences governing which screen names or subscribers can send buddyicons to the client 702 b (step 720 b). The second subscriber may chooseto never display buddy icons. When this option is set, the subscriberwill not be able to see any buddy icons that have been chosen for otherbuddies. The second subscriber may select to never accept buddy icons.When this option is selected, the second subscriber is still able to seebuddy icons that the second subscriber has chosen for other buddies. Thesecond subscriber may select to accept buddy icons from users on thesecond subscribers Buddy List®. When this option is selected, the secondsubscriber will accept buddy icons from only familiar buddies that havebeen added to the subscribers Buddy List®. The second subscriber alsomay display a buddy icon knock-knock dialogue. When the option isselected, the second subscriber is alerted when a buddy desires to senda buddy icon. When this option is disabled, the second subscriberautomatically receives buddy icons from users without any warning. Inthe procedure 700, it is assumed that the second subscriber has selectedto display the buddy icon knock-knock dialogue.

After the first subscriber associated with the first client 702 a hasdesignated a graphical image as a buddy icon (step 720 a), the firstsubscriber uses the first client 702 a to communicate with the secondsubscriber. In particular, the first subscriber uses the first client702 a to send an instant message addressed to the second subscriberalong with image data corresponding to the buddy icon (step 725). Thehost 704 receives the message addressed to the second subscriber alongwith the image data (step 730). In one implementation, the host 704 isan IM host. The host 704 then authenticates the message addressed to thesecond subscriber (step 735). Typically, authentication is accomplishedby confirming that the sender and the addressee of the message areregistered subscribers of the host 704. Once the message has beenauthenticated , the host 704 sends the message and the image data to thesecond subscriber (step 740).

The client 702 b receives the message and the image data associated withthe buddy icon of the first subscriber from the host 704 (step 745). Theclient 702 b then displays a blurred view of the buddy icon (step 750 a)and also displays the message sent from the first subscriber (step 750b). In one implementation, the blurred view of the buddy icon isdisplayed in a knock-knock dialogue box. The knock-knock dialogue boxmay be presented to the second subscriber prior to the message from thefirst subscriber. Alternatively, the knock-knock dialogue box mayoverlay the message dialogue box.

When presented with the blurred view of the buddy icon, the secondsubscriber uses the second client 702 b to accept or reject the buddyicon (step 755). The second subscriber may immediately accept the buddyicon from the first subscriber. In this case, a clear view of the buddyicon is rendered in the instant message dialogue box. The secondsubscriber also may immediately reject the buddy icon. In this case, thebuddy icon is not presented to the second subscriber.

In some cases, however, the second subscriber may be unsure whether toaccept or reject the buddy icon. In this case, the second subscriber maysharpen the view of the buddy icon (step 760). When the view of thebuddy icon is sharpened, the second subscriber is presented with abetter view of the buddy icon and can therefore make a more informeddecision as to whether to accept or reject the buddy icon. After theview of the buddy icon is sharpened (step 760), the second subscriberagain can choose whether to accept or reject the buddy icon (step 755).

In one implementation, the buddy icon is a 48×48 pixel image. When thesecond client 702 b receives the image data from the host 704, thesecond client 702 b displays every eighth pixel to the secondsubscriber. When the second subscriber selects to sharpen the view ofthe buddy icon, the second client 702 b displays every fourth pixel tothe second subscriber. If the second subscriber chooses to sharpen theview of the buddy icon again, the second client 702 b displays everyother pixel to the second subscriber. Finally, if the second subscriberagain sharpens the view of the buddy icon, the second client 702 bdisplays the clear view of the buddy icon to the second subscriber. Ifat any time, the second subscriber suspects that the buddy icon isobjectionable, the second subscriber has the option to reject the buddyicon. By presenting the second subscriber with a very poor resolutionimage and then gradually improving the resolution of the image, thesecond subscriber will be less likely to view an objectionable image.

In general, the client 702 a and the client 702 b communicate over anopen connection, such as an open TCP connection established through thehost 704. Typically, both clients 702 a, 702 b include a Winsock API forestablishing an open TCP connection to the host 704 and a clientapplication for accessing the host 704. The client devices 702 a, 702 bconnect to the host 704 to establish the connection.

The clients 702 a, 702 b can use the connection to communicate with thehost 704 and with each other. The connection remains open during thetime that the first client 702 a and the second client 702 b areaccessing the host 704. To access the host 704, each client 702 a, 702 bsends a request to the host 704. The requests identify the associatedsubscribers to the host 704 and to other subscribers using thesubscribers' unique screen names. The host 704 verifies a subscriber'sinformation (e.g., screen name and password) against data stored in asubscriber database. If the subscriber's information is verified, thehost 704 authorizes access. If the subscriber's information is notverified, the host 704 denies access and sends an error message.

Upon accessing the host 704, the client 702 a receives a list of thefirst subscriber's “buddies” that are currently online (i.e., accessingthe host 704). Buddies are subscribers or screen names designated forexchanging instant messages. In general, the host 704 informs the firstsubscriber as to whether designated buddies are online or offline. Thehost 704 also informs any subscriber that has designated the firstsubscriber as a buddy that the first subscriber is online. The firstsubscriber can use an application running on the client 702 a (“theclient application”) to view the online status of particular buddies,exchange instant messages with online buddies, participate in group chatrooms, trade files such as pictures, invitations or documents, findother subscribers with similar interests, get customized news and stockquotes, and search the Web. Additionally, the subscriber can use theclient application to transfer one or more files to or from the clientdevice of another subscriber.

In one implementation, the client 702 b attempts to establish a directsocket connection (e.g., a peer-to-peer socket connection) to the client702 a using the IP address of the client 702 a. In some circumstances,however, the client 702 b may be unable to establish a direct socketconnection to the client 702 a, such as, for example, when the client702 a is behind a firewall. In the event that the client 702 b cannotestablish a direct socket connection to the client 702 a after apredetermined time period, the client 702 b sends a connect message tothe client 702 a through the host 704. The connect message includes, forexample, the message type, the screen name of the first subscriber, thescreen name of the second subscriber, the IP address of the client 702b, and a randomly generated security number. The host 704 authenticatesthat the connect message from the client 702 b is from a validsubscriber and then sends the connect message to the client 702 a.

Upon receiving the connect message, the client 702 a attempts toestablish a direct socket connection to the client 702 b of the secondsubscriber using the IP address of the client 702 b. If, however, theclient 702 a is unable to establish a direct socket connection to theclient 702 b, such as, for example, when the client 702 b is behind afirewall, the client 702 a displays a message to that effect and sendsan error message to the client 702 b through the host 704. The host 704authenticates that the error message from the client 702 a is from avalid subscriber and then sends the error message to the client 702 b ofthe second subscriber. In response to the received error message, theclient 702 b displays a message to the subscriber.

If a direct socket connection has been established between the client702 a and the client 702 b, the client 702 b verifies that the client702 a includes a valid client application by, for example, verifying thesecurity number of the client application.

The direct connection bypasses the connection between the client 702 aand the host 704. In one implementation, the host 704 limits thecapacity of the connection to the client 702 a. As a result, the client702 a cannot transfer files larger than a threshold file size (e.g. 8000characters or bytes) through the host 704. In contrast to the capacityof the connection between the client 702 a and the host 704, thecapacity of the direct socket connection between the client 702 a andthe client 702 b is not limited. The client 702 a, therefore, maytransfer relatively large files (e.g. graphics files, executable files)to the client 702 b.

FIGS. 8-11 illustrate examples of graphical user interfaces (“UIs”) thatmay be presented to subscribers. In general, a graphical UI will berendered on a subscriber's client device.

Referring to FIG. 8, a UI 800 includes a Buddy Icon preference box 805.A subscriber may use the Buddy Icon preference box 805 to set transferpreferences for buddy icons as well as to designate graphical images tobe used as buddy icons. In one implementation, the Buddy Icon preferencebox 805 is used to select a subscriber's own buddy icon to be presentedto other subscribers.

Referring to FIG. 9, a UI 900 includes a Buddy Icon preference box 905.In one implementation, the Buddy Icon preference box 905 is used todesignate a buddy icon for a selected buddy.

Referring to FIGS. 10A-10D, UI's 1000A-1000D include Accept Buddy Icondialogue boxes 1005A-1005D. The Accept Buddy Icon dialogue boxes1005A-1005D illustrate the progression of knock-knock dialogue boxespresented to a subscriber. That is, accept buddy icon dialogue box 1005Bresults from selecting the sharpen button in Accept Buddy Icon dialoguebox 1005A. Likewise, Accept Buddy Icon dialogue box 1005C results fromselecting the sharpened button in Accept Buddy Icon dialogue box 1005B.Finally, a clear view of the buddy icon image is presented in AcceptBuddy Icon dialogue box 1005D from selecting the sharpen button inAccept Buddy Icon dialogue box 1005C.

Referring to FIG. 11, a UI 1100 includes an instant message dialogue box1105. In one implementation, the instant message dialogue box 1105includes a buddy icon 1110. The buddy icon 1110 is rendered in theinstant message dialogue box 1105 when designated as the buddy icon forthe selected buddy and/or when the buddy icon is selected by a buddy andaccepted by the subscriber.

Although the examples above are described in conjunction with an instantmessaging system, aspects may be applicable to other forms ofcommunication, such as e-mail. Other embodiments are within the scope ofthe following claims.

What is claimed is:
 1. A method for displaying a buddy icon sent betweenfirst and second subscribers of an instant messaging system, the methodcomprising: receiving, from the first subscriber, a buddy icon;obscuring the clarity of the received buddy icon; displaying theobscured buddy icon to the second subscriber; receiving input from thesecond subscriber indicating a willingness to enhance the clarity of theobscured buddy icon; and enchancing the clarity of the obscured buddyicon in response to the input from the second subscriber.
 2. The methodof claim 1 wherein obscuring the clarity of the buddy icon comprisesreducing a resolution of the buddy icon to create a poor resolutionbuddy icon.
 3. The method of claim 2, wherein enchancing the clarity ofthe obscured buddy icon comprises increasing the resolution of the poorresolution buddy icon.
 4. The method of claim 1, wherein the buddy iconis compressed to a standardized image size.
 5. The method of claim 1,further comprising setting preferences for receiving buddy icons.
 6. Themethod of claim 5, wherein setting preferences comprises presenting agraphical user interface to the second subscriber.
 7. The method ofclaim 1, further comprising allowing the second subscriber to reject thebuddy icon.
 8. The method of claim 7, wherein allowing the secondsubscriber to reject the buddy icon comprises presenting a graphicaluser interface to the second subscriber.
 9. The method of claim 1,further comprising displaying an instant message concurrently with theobscured buddy icon in a separate dialog box.
 10. The method of claim 1,wherein receiving the buddy icon comprises receiving all image data forthe buddy icon, and obscuring the clarity of the buddy icon comprisesreducing the image data to less than all of the image data.
 11. Acomputer program for a displaying a buddy icon sent between first andsecond subscribers of an instant messaging system, the computer programbeing stored on a computer readable medium and comprising instructionsfor: receiving, from the first subscriber, a buddy icon; obscuring theclarity of the received buddy icon; displaying the obscured buddy iconto the second subscriber; receiving input from the second subscriberindicating a willingness to enhance the clarity of the obscured buddyicon; and enhancing the clarity of the obscured buddy icon in responseto the input from the second subscriber.
 12. The computer program ofclaim 11, the computer readable medium comprising a disc.
 13. Thecomputer program of claim 11, the computer readable medium comprising aclient device.
 14. The computer program of claim 11, the computerreadable medium comprising a host device.
 15. The computer program ofclaim 11, the computer readable medium comprising a propagated signal.16. A communications apparatus for displaying buddy icon sent betweenfirst and second subscribers of an instant messaging system, theapparatus comprising: means for receiving, from the first subscriber, abuddy icon; means for obscuring the clarity of the received buddy icon;means for displaying the obscured buddy icon to the second subscriber;means for receiving input from the second subscriber indicating awillingness to enhance the clarity of the obscured buddy icon; and meansfor enhancing the clarity of the obscured buddy icon in response to theinput from the second subscriber.
 17. An instant messaging program thatallows a first subscriber to send instant messages and buddy icons to asecond subscriber the program comprising: a first interface elementconfigured to obscure the clarity of a buddy icon associated with thefirst subscriber and to display the obscured buddy icon to the secondsubscriber; and a second interface element configured to receive inputfrom the second subscriber indicating a willingness to enhance theclarity of the obscured buddy icon; wherein the first interface elementis configured to enhance the clarity of the obscured buddy icon inresponse to the input from the second subscriber.
 18. Thie program ofclaim 17 wherein the first interface element is configured to obscurethe clarity of the buddy icon by reducing a resolution of the buddyicon.
 19. The program of claim 18 wherein the first interface element isconfigured to enhance the clarity of the obscured buddy icon byincreasing the resolution of the obscured buddy icon.
 20. The program ofclaim 17 wherein the buddy icon is in a standardized image size.
 21. Theprogram of claim 17 further comprising a third interface element forsetting preferences for receiving buddy icons.
 22. The program of claim17 further comprising a third interface element for allowing the secondsubscriber to reject the image.
 23. The program of claim 17 furthercomprising a third interface element for displaying an instant messageconcurrently with the obscured buddy icon.
 24. The program of claim 17wherein the program receives all image data for the buddy icon and thefirst interface element is configured to obscure the clarity of thebuddy icon by reducing the image data to less than all of the imagedata.